Repository navigation
Add a Dockerfile, compose file and guide to run FlyBot in a container - #482
Merged
Merged
Conversation
Collaborator
Author
|
Self-review: PASS
|
This was referenced Oct 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #352
What. First slice per the Owner decision (option a): a
Dockerfile,compose.yamland a short guide (docs/docker.md, docs/docker.zh.md) to run one FlyBot per person on a Linux box. You build the image yourself; nothing is published or deployed.core+plugins/{social,tree,timeline}withcheck-pack.mjs(the release tarballs), runtimenode:24-bookworm-slim+ DSH0.2.0-rc.2(pinned like the README) + pnpm + tini. Usernode(uid 1000), one volume/data, health check, no keys or tokens in the image (.dockerignoredrops.env,.credentials.yaml,.dsh*)./data/profiles/web(yourcordis.patch.ymland own plugins are kept), then runsdsh web. Sign-in stays DSH's own?token=link (indocker compose logs).compose.yamlpublishes the port on the host's127.0.0.1only;DEEPSEEK_API_KEYis passed through only when set. Remote access: your own HTTPS proxy or SSH tunnel.0.0.0.0through a profile overlay (docker/web.patch.yml; the webserver config allows it, the CLI flag refuses it). That reaches only the container's network; the DSH Host/Origin fence and token still apply.Dockerworkflow (only when these files change) builds the image,compose up --waiton the health check, checks401on the loopback port, the printed sign-in line (never shown), non-root uid and the linked packages. No push, no registry login.release.ymlis untouched.Test.
ARCH_DOCS_BASE=origin/main TZ=UTC npm run verifypasses (0 failures), including the new.github/scripts/docker-profile.test.mjs. Locally without Docker: randocker/entrypoint.mjsagainst the packed packages and the harness DSH: started, health check OK,401unauthenticated, token link →303→200, foreign Host →403, SIGTERM stops it. actionlint clean. Docker is not installed on the dev box, so the image build itself is checked by theDockerworkflow on this PR.Risk tier: T3 (estimate; the controller sets the label) — adds a workflow under
.github/.